Just in case it is of interest to anyone else, I did finally solve this problem and have had a repeat and resolved again.

The fix at the time was to reset the suspect flag, restart the instance and restore the next tlog file. It seems that the failure is actually occurring during the final stages of restore and may relate to the log shipping being a third party routine that is running as a remote stored proc and being timed out.