This is because replacing it with ``emplace_back`` could cause a leak of this
pointer if ``emplace_back`` would throw exception before emplacement (e.g. not
-enough memory to add new element).
+enough memory to add a new element).
For more info read item 42 - "Consider emplacement instead of insertion." of
Scott Meyers "Effective Modern C++".
other classes use the :option:`SmartPointers` option.
-Check also fires if any argument of constructor call would be:
+Check also doesn't fire if any argument of the constructor call would be:
- - bitfield (bitfields can't bind to rvalue/universal reference)
+ - a bit-field (bit-fields can't bind to rvalue/universal reference)
- - ``new`` expression (to avoid leak) or if the argument would be converted via
- derived-to-base cast.
+ - a ``new`` expression (to avoid leak)
-This check requires C++11 of higher to run.
+ - if the argument would be converted via derived-to-base cast.
+
+This check requires C++11 or higher to run.
Options
-------