Describe the bug
While working on #8770, it turns out that the reading of std::vector<T> in RNTuple appears to be affected by memory leaks, if ``T` allocates memory in its constructor. This should be fixed and unit-tested, with a custom class that tracks constructor and destructor calls.