Custom Memory Allocator

Using a custom memory allocator with standard library containers

When trying out our custom memory manager with a specific type, it worked great! There is a problem, though. It turns out that the class-specific operator new is not called on all the occasions we might have expected. Consider the following code: