Bah, thanks for finding that and reporting it. Just fixed it and bumped the version number of wp-super-cache up.