Certainly true, but you do not need to provide a copy-constructor (actually, in most cases it is harmful to do one by hand) since the compiler will generate one for you (provided all members can be copied).
I just wanted to point out, that a missing object to which the temporary data could be copied to, will result in trouble. E.g. by returning a temporary object which will be passed to a function call using references. He although returns only a reference to the "interface", so a copy-constructor wouldn't work without casting, thought an overwritten assignment operator using RTTI could construct a valid copy... (would this be really possible,hmmm). But, please, don't do this, this would be really evil.