Another fix to mightConstraint: it was only checking (i,j) pairs that
were in different row AND column than (x,y); it should have been "OR".