I have a memory class that I really enjoy using. There are a couple of issues though:
1) Is there a way to invoke the constructor and destructor manually on items returned from the pool such that the memory is not freed, just the functions called?
2) if a user explicitly calls delete on an item, the items contents (or rather, the chunk within the pool) should not be freed since the underlying C/C++ lookup mechanisms won't find it to be a new'd/malloc'd pointer, correct?
3) I am really trying to avoid overriding new/delete globally.
4) I KNOW I can't override malloc/free, so I really hope assumption #2 is correct.