No, I do not care whether Coverity considers this a memory leak.
It's entirely not worth the code space to do it correctly.