"Inconsistency in Target" Rule bug (version-related)

There two different source segments (one has a tag, the other does not) and the latest Xbench treated them as the same source, thus gave the result “Inconsistency in Target” and vice versa.
It appears in latest version build 1520 64bit and does not appear in build 13xx.

More screenshots

Different target segments (one has a tag, the other two do not) with the result “Inconsistency in Source”.

This is not a bug. When checking inconsistencies in source or target, tags are ignored to detect the maximum number of errors.

Thanks for your reply.
“to detect the maximum number of errors” is great.
However can we have an option to enable/disable this feature? If there are multiple entries like this, it can be overwhelming.