You don't have create expectations up-front. All you need to do is tell the container that you intend to test that dependency afterwards. The simplest way to do it is like so:
var c =
c.Assert<ITargetDependency>(x => x.ShouldBeCalled());
The ToMock() binding then allows you to do assertions on that instance.
Granted, this appears to be a needless complication in this extremely simple and straightforward scenario. I'll fix the code so that this scenario will no longer require the ToMock() binding and your second listing will then just work. The fix will be made available in our upcoming internal build due next week.
As a token of gratitude for uncovering and reporting this issue, I've granted you some Telerik points.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.