Non-Virtuals Call Protected Non-Overloaded Virtuals idiom

[ittium]

Group,
My doubt is regarding Public Overloaded Non-Virtuals Call Protected
Non-Overloaded Virtuals idiom, defined as part of following FAQ.
http://www.parashift.com/c++-faq-lite/strange-inheritance.html#faq-23.3.

Here to avoid hiding of overloaded (virtual/non-virtual) functions it is
suggested that these functions be made non-virtual (if originally
virtual) and call non-overloaded virtual versions providing similar
functionality.

I am not sure how this is solving the issue, since although not virtual
now, overloaded function will still be inherited by derived class and
derived class still can hide the function by defining overloaded
function with the same name.
thanks
Ittium