Quote:This would imply that you have control over the function's signature. And if you do, then it's preferable to use a 'passing style' which correctly represents ownership:

That sounds reasonable if you're the sole developer in a smallish project, but looks to break down under real-world maintenance.
It's unlikely that every corner of the codebase uses these semantics, so the rule may not be clear to junior coders. What's to prevent them from taking the address and storing it? Writing a "if you use & on this parameter, you will be shot/fired" comment in all of these spots would be tiresome. Sure, they could still store ptr.get(), but at least those spots can be found, unlike operator&.