A Compiled Module is there to allow you to create global functions that can be used across the board.
Recorded analog mouse movements, and check point information are script level. They aren't a global action, but a specific individual test action. Including them in a Compiled Module does not follow their use.
In this case, WinRunner had the foresight implemented to not allow you to code these items in a way inconsistent with their use. It is an issue of scope, which you are getting confused between Compiled Modules and Test Script actions.
Insanity: doing the same thing over and over again and expecting different results