Comment 2 for bug 1286611

Would you like to delegate the responsibility for object deletion to more dedicated classes?
Would it be useful to get rid of explicit delete calls in your own source code?

How do you think about information from sources like the following?

* http://smart-pointers.sourceforge.net/#Description

* FAQ "How should I handle resources if my constructors may throw exceptions?"
  http://www.parashift.com/c++-faq/selfcleaning-members.html

* Answers for the question "Is memory allocated for an object automatically deleted if an exception is thrown in a constructor?"
  http://stackoverflow.com/questions/4717656/is-memory-allocated-for-an-object-automatically-deleted-if-an-exception-is-throw

* Yonat Sharon:
  http://ootips.org/yonat/4dev/smart-pointers.html#WhyExceptions

* Article "Constructor Exceptions in C++, C#, and Java" by Herb Sutter
  http://herbsutter.com/2008/07/25/constructor-exceptions-in-c-c-and-java/