Temp workaround: force out-of-block modification for properties with nullable types

Initializers for properties with nullable types are analyzed with binding context common for all declarations.
This can cause invalid elements are left in the cache guarded with out-of-block  modification tracker. This workaround forces increment for such cases.

compiler/jet.as.java.psi/src/org/jetbrains/jet/asJava/KotlinCodeBlockModificationListener.kt

@@ -125,11 +125,6 @@ public class KotlinCodeBlockModificationListener(modificationTracker: PsiModific
                 }
                 is JetProperty -> {
                     val property = blockDeclarationCandidate : JetProperty
-                    val typeReference = property.getTypeReference()
-                    if (typeReference != null && property.getInitializer().isAncestorOf(element)) {
-                        return true
-                    }
-
                     for (accessor in property.getAccessors()) {
                         when {
                             accessor.getInitializer().isAncestorOf(element) -> return true