If you look at the description on the Wikpedia article, it sounds like the principle applies to any implementation in which some of the flow control is handled by a framework which calls the code you write.
My favorite use case of this is dependency injection (DI). In this pattern, the flow control for determining where/how to get a dependency is inverted, i.e. the framework provides the dependency reference to your code as opposed to having yourself do it programmatically (by calling constructors, factory methods, etc...).