How the compiler back-end can influence warnings.
Avoiding using an object after is has destructed, and maybe using a less-well-known corner of the C++ language.
The handle remains valid for the object's lifetime, but what is the object's lifetime?
The cost depends on the performance counter.
Keeping them from colliding with each other.
Forcing named return value optimization.
You want them to go first, but you also want to deduce them.
You can get a little bit of the way there.
I see what you did there.
A little-known system configuration setting.
