> The v-table function generated if the method is moved inside the class/struct winds up being identical.
Unless you add some additional semantics/keywords, it's not going to create a vtable.
> Dunno what it is, some kind of familiarity bias with the way the code is laid out I guess, not coming from OOP languages.
I'm sure that's what it is.