https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80658
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- Using the default configuration GLIBCPP_FORCE_NEW has not made any difference to std::allocator since 2005 when r106665 was committed, changing the default back to the allocator based on new/delete. So if GLIBCPP_FORCE_NEW made a difference then the blog post seems to be about GCC 3.4 or something of that age, and a bug report about ancient history is useless.
