The behavior you reported has been confirmed as a bug in 2.0d and prior versions. A new version of Ultra Recall, version 2.0e, has been released which addresses it. Please download and install the latest version of Ultra Recall 2.0 to obtain the fix for this bug.
You can view the entire list of changes in UR 2.0e in the Ultra Recall version history
FAQ entry.