Although Verification Manager itself can be used without change, adopting Loosely Coupled Comprehensive Verification requires more work and more invasive changes than the other subsystems. The first and most critical step is to define the interface between test cases and Verification. The methods that make up this interface can be of any scope and organized in any fashion you like, but each Begin/End pair must enclose a well-defined set of actions whose consequences can be reliably predicted from the input parameters. This can be a difficult task at first, but it is ultimately a rewarding one.
Once your interface is defined you can stub out the methods on the Verification side and then modify your test cases to call the Begin and End methods at the appropriate locations.
Finally, move the expected state data generation from your test cases into the various Expected State Generators. In many cases you will be able to simply remove the post-action state verification from your test cases, but at times you will need to augment the built-in state comparators to handle data types specific to your application.