make_shared underused

The use of make_shared (and family) to construct shared_ptr (and other)
instances is highly encouraged because of its benefits over using new and
smart-pointer ctor or reset. (Mainly better memory and cache coherence and
minimizing potential memory leaks.)

A quick survey of the LO code shows that this idiom is underutilized.

Is this an unintentional coincidence that we're encouraged to cleanup, or
is there a policy as-such?

Thanks.