Some publications do not recommend to use object pooling, especially for objects that only use memory and hold no external resources [[http://www.ibm.com/developerworks/java/library/j-jtp11253/]. Opponents usually say that within modern languages with garbage collector the costoperator "new" needs only 10 instructions or about when than classic "new" - "delete" pair requires hundreds of allocatingthem anas objectit isdoes notmore complex highwork. Also, the most of garbage collectors scan "live" object references and not the memory that these objects use for they content. This means that any number of "dead" objects without references can be discarded with the little cost. Differently, keeping the large number of "live" but unused objects increases duration of the garbage collection [[http://www-128.ibm.com/developerworks/java/library/j-jtp09275.html?ca=dgr-jw22JavaUrbanLegends]]. Some works demonstrate that removalRemoval of the direct memory management (putting the garbage collector instead) in the most cases actually make programs to run faster [http://www.cs.ubc.ca/local/reading/proceedings/spe91-95/spe/vol23/issue7/spe836.pdf].
