CallerMemberName not that great for INotifyPropertyChanged

I've blogged before about the perf improvements of using the CallerMemberName attribute over an expression tree to avoid using hard-coded property strings names when firing the PropertyChanged event on INotifyPropertyChanged.

This works great for the majority simple cases.

Setting the property & notifying:

 or just notifying:

The problem is when it's not the simple case - when setting a property on a view model and wanting to force the updating of another property (on the view model) it doesn't work obviously.

At this point I'm thinking I'll go back to the expression tree approach.