> There are of course cases when you need to deal with types that are not well behaved. If you can tolerate a memory allocation per object, the simple solution

> There are of course cases when you need to deal with types that are not well behaved. If you can tolerate a memory allocation per object, the simple solution is to use unique_ptr. But unique_ptr definitely does not satisfy TFA's `concept WellBehaved`...? I mean, the idea of a "concept WellBehaved" is pretty intriguing (albeit completely unattested in practice AFAIK), but TFA should have spent a minute coming up with a concept definition that actually works before posting.