I had similar things once I turned on this option in the legacy code I manage.
All that was required was to add a few MyInterfaceReference := nil statements in the destructors of classes where the class kept an interface reference as a field. I'd not been explicitly nilling references until then and relied on the reference counting to handle it for me. I saw no other side-effects from the 'use of freed instances' issue before or after the code change - I just left it in to stop FastMM4 moaning about them.