Re: Why scoped_ptr dost provide custom deallocation?

To a certain degree auto_ptr<YourClass> supports a custom de-allocator...overload operator delete in a known case for a specific object. I haven't actually done it, but it seems not too challenging to template a base class that does this for you with your custom allocator and then use it as a mix-in class for whatever class you are creating. Does that solve your issue or am I missing your point? If so, sorry I came a little late to this thread.

Not exactly: I cannot subclass the object which I want to use (DOMWriter from the Xerces lib), because it has hidden constructors. So the question still remains remains about theauto_ptr custom deallocator...