After adding 25 pano items and a pretty background (which worked wonderfully in the WP7 emulator) I sat back had a cup of tea then thought about trying it on a device.
Despite unloading pano items and loading pano item contents on demand, it seems the sheer number of pano items was enough to bring my app to its knees. Clearly the panorama control is not designed for 25 pano items but I write this as a warning for anyone who is only able to test on an emulator.
Also it may not blow up (by blow up I mean return to the phone menu, the debugger disconnecting and no errors logged) on the page with all these pano items on. Indeed it blew up on the next page down (temporarily cured by removing the background image which must have reduced the memory just enough to prolong the apps life for a few seconds – however some back presses later and kablamo again).
Make sure you keep an eye on these:
long deviceTotalMemory = (long)DeviceExtendedProperties.GetValue("DeviceTotalMemory") / 1024; long applicationCurrentMemoryUsage = (long)DeviceExtendedProperties.GetValue("ApplicationCurrentMemoryUsage") / 1024; long applicationPeakMemoryUsage = (long)DeviceExtendedProperties.GetValue("ApplicationPeakMemoryUsage") / 1024;