This basically tells that calling non-virtual function through a pointer/reference to a base class will call a method of the base class.
NAD.

Also, typeid(obj) for a non-polymorphic type only depends on the static type of the expression obj.

@jwakely I don't think an unevaluated operand expression interprets values of objects, because it doesn't even access them.

And whether that's an unevaluated operand or not depends on whether it's a polymorphic type. The interpretation of obj in that context depends on the static type. The interpretation of dynamic_cast<X&>(obj) can also depend on the static type of obj. When it's a polymorphic type the information associated with the object is used "to determine the object's type during program execution". For other objects, it isn't.

Looks like my opinion that this wording is an artifact left from the «object is a region of storage» times is correct. That definition of object and the last sentence of [intro.object]/1 were copied from the C standard.