Using virtual-C++ vs MFc

I am stuck with a doubt! I have been working with MFC based applications for sometime. Decided to read up some theory to strengthen my fundamentals. Naturally, I was reading MFC concepts as well as C++ basics. What struck me was the way we use VIRTUAL in both.

In C++, there goes a standard way to use virtual functions.
- There is a Base class B having a function func() and its derived class D also uses/implements the function func(). If a function creates objects of both B and D and calls this func() through a pointer to B, the base class version of this function will be called UNLESS we declare func() as virtual .right??? So if we want to call func() from D's implemetation, we declare func() as virtual in Base class B , pass a reference of D's object to base class B's pointer and then call func() thru this pointer. I guess i got this right so far???

Now, how do we go about it in MFC(which is also supposed to be C++ at the end of the day)? From what I have used so far..i use virtual funcs like this.

Class CDialog has 3 virtual functions. Lets take OnInitDialog() as the example.

This takes care of calling the derived class version of OnInitDialog() despite the fact that OnInitDialog is a virtual function inthe base class. We didn't assign any reference of myDlg to a base class pointer or anything??????????????????????????

Am i missing something or are they implemented differently in C++ and MFC programming????????

So would the same logic be applied to all virtual functions overridden in MFC?(functions of CObject, of CWinApp, InitInstance etc.) Is it correct to say that most of these virtual functions which are overridden are downcasted/typecasted and the correct version of the function is called??

So would the same logic be applied to all virtual functions overridden in MFC?(functions of CObject, of CWinApp, InitInstance etc.) Is it correct to say that most of these virtual functions which are overridden are downcasted/typecasted and the correct version of the function is called??