Second, don’t manually delete the resource out from underneath the std::unique_ptr.

Use std::make_unique() instead of creating std::unique_ptr and using new yourself.

Favor std::array, std::vector, or std::string over a smart pointer managing a fixed array, dynamic array, or C-style string.

Because std::unique_ptr is designed with move semantics in mind, copy initialization and copy assignment are disabled. If you want to transfer the contents managed by std::unique_ptr, you must use move semantics.