The CycleStamp() accessor for SceMiMessageData objects is presented in the spec (p52, PDF 60) 
without any description of what would happen if a renegade user were to call it on a SceMiMessageData object not originating from an OutputPortProxy. Should the accessor call the port's error handler in this case, return 0, or is "undefined behavior" adequate?