We do not support evaluating bitwise operations, so that when we check for
their results being null we create a new assumption whether the current new
symbol is null or non-null. If we are on the non-null assumption's branch
we need to check the left-hand side operand's constraint range informations:
- It if contradicts with the forming new constraint ranges then we create a null state as it is an impossible condition.
- Otherwise we need to remove the nullability from its ranges as we know that it cannot be null on that branch (except bitwise OR).