C.82 please recommend alternative to virtual function calls in constructor/destructor

C.82: Don’t call virtual functions in constructors and destructors
Just to be clear up front. I understand that virtual dispatch in a constructor is not a valid "alternative" because it simply doesn't work.

The guidelines identify two cases where an call to a virtual function is acceptable

1. If the function is final and therefore virtual and non-virtual dispatch will have the same effect
2. If the function is explicitly qualified so it's not actually a virtual call at all

As such in the scenario where I encounter or want to write code that violates this rule I have these options:

1. mark the function final
2. call the function explicitly
3. extract the functionality of the function into a separate non-virtual function which the virtual function calls

My question is which is the preferred solution?

That's the question. My proposed answer is to combine 1 and 2 so that it's obvious to anyone reading the calling code and anyone hoping to override the function what is going on. If the function can't be final because it's overridden later then my instinct is to use 3. However I think 1 is usually a valid option because the average inheritance heirarchy isn't very deep in my experience (often just a interface with a handful of concrete implementations).

Start with the linked C.82 guideline and review the three alternatives described in the issue. Determine which option should be preferred, including when a function cannot be marked final, and document a clear recommendation; completion requires agreement on the guidance and an update to C.82.