Should I normally use pointers to freestore allocated objects for my data members, or should I use "composition"?, C++ FAQ

C++ FAQ

From Marshall Cline: Bjarne Stroustrup, Herb Sutter, Andrei Alexandrescu, Pearson / Addison-Wesley Publishers and I collaborated to create a new C++ Super-FAQ! It's a team effort, with huge contributions from each of us and with amazing support from dozens of brilliant editors. The result is "awesomer" than ever! I originally wrote/published the FAQ in 1991 and now look forward to this new phase - and to continue working with it for another 20 years!

On a personal note, I'm at Oculus VR and it is amazing - fabulous people doing fabulous work. We're hiring more fabulous people so write me if that's you!

FAQ: Should I normally use pointers to freestore allocated objects for my data members, or should I use "composition"? ←(in the new Super-FAQ)

It's in Section: Reference and value semantics:

FAQ: What is value and/or reference semantics, and which is best in C++?
FAQ: What is "virtual data," and how-can / why-would I use it in C++?
FAQ: What's the difference between virtual data and dynamic data?
FAQ: Should I normally use pointers to freestore allocated objects for my data members, or should I use "composition"? (this FAQ)
FAQ: What are relative costs of the 3 performance hits associated with allocating member objects from the freestore?
FAQ: Are "inline virtual" member functions ever actually "inlined"?
FAQ: Sounds like I should never use reference semantics, right?
FAQ: Does the poor performance of reference semantics mean I should pass-by-value?