The presence of a vtable in a class simply supplying a 4-byte ref-count causes the size of the each subclass to grow by 4/12b (32/64-bit). There appears to be no reason for the virtual dtor, in particular as it's already also protected.

However, any subclass of it may rely on the virtuality of the dtor, so we need to proceed with caution and enlist the compiler's help each step of the way of removing virtualness of dtors down the hierarchy.