Good thing that the author provided such an exhaustive list of arguments supporting his opinions. Oh wait. Between using pointers and the standard library, I think that I will stick with pointers.
To me at least build_new_object example seems horribly wrong: If you allocate the object on the stack and then returns it, it will go out of scope with the function, and the memory overwritten with next stack usage. Or does modern C++ do some magic nowadays?
No it will use a copy or move constructor to return the object by value, no problem there. Notice the value is being returned, not a pointer to the value.
