Can I assume allocators don't hold their memory pool directly (and can therefore be copied)?

In C++11 section 17.6.3.5 Allocator requirements allocator. Requirements specifies the requirements for conforming allocators. Among the requirements are.

The old C++ standard makes requirements for a standard-compliant allocator: These requirements include that if you have Alloc a, b, then a == b, and you can use be to deallocate things that were allocated with a. Allocators are fundamentally stateless.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.