Totally approve of testing the lack of spurious 'Released lock' messages here.  Could you explain how advancing the clock by one before the lock is created will trigger that though?  I thought the spurious messages would just be because it attempted to acquire the lock, failed to due to either no such claim ID or the wrong claim ID being present?