changing >= to != to look for inconsistencies in both directions

It /seems/ equally bad to have a seq_region.length that is either shorter than (clearly wrong) or longer than (wrong I think) than the longest corresponding entry in the assembly table for the seq_region. Note that the link to the 'asm' side of the assembly table precludes sequence_level seq_regions... I expect...

See what you think,
Dan.