There should be a clearer separation of concerns where the resource manager is responsible for the state changes of the ExternalResource object so that we do not need constructs like:

[pseudocode]
manager.lock(resource, "Locked by me")
resource.setLocked(info)
// Do some work before unlocking...
manager.release(resource)
resource.setLocked(null)