BN should be smart enough to reference the inherited class when necessary

Version and Platform (required):

• Binary Ninja Version: 3.6.4790-dev, 10b89271
• OS: macos
• OS Version: 14.3
• CPU Architecture: arm64

Bug Description:
I'm uncertain whether this is a bug or a missing feature. In the current implementation, if a reference is made to the base class of the derived class, BN displays it as shown in the example below:

Actually, the reference here is not to the VFT, but to the class itself, even if technically they are the same. It would be preferable if BN were intelligent enough to reference it as something like this->Pet.

Cat class is defined as follows:

class __base(Animal, 0) __base(Pet, 0x18) Cat

Hence, BN has information indicating that when offset 0x18 is directly referenced, it could actually be referencing the Pet class depending on the context. For instance, if this reference occurs for a function parameter and the target parameter type is Pet* (as shown in the screenshot), BN could display it as this->Pet.

Of course, there will be situations (as can also be seen in the screenshot) where references are made to the Pet class's VFT. However, I believe it is predictable whether the reference is made to the class or the VFT.

Start by reproducing the example on Binary Ninja 3.6.4790-dev for macOS arm64, using the shown Cat inheritance declaration and the reference whose parameter type is Pet*. Determine how the current display distinguishes a class reference from the Pet virtual-function table, then verify that class references render contextually as this->Pet without changing VFT references.