>That's almost, but not quite, true. The real problem is that delete *always* >calls the destructor. the original sender may have meant something different: you can manipulate the allocator directly and invoke things like destroy and deallocate explicitly, thus decoupling these functionalities instead of using the coarser 'delete' statement. --Sylvain