Currently, LDAPConnectionOptions gets copied numerous times as it is derived from the default options and propagated into a particular connection. The propagation mostly involves pass by reference into various local variables, which makes it challenging to determine ownership. It also contrasts with the updated approach used for LDAPBindOptions, which involves constructing a unique_ptr in the LDAPRunner and moving it into the eventual LDAPConnection.

Adopting a similar approach for LDAPConnectionOptions would help make the code clearer and easier to follow and minimize risk of ownership/lifetime bugs seen in the past.