I've just hit this in 2022.3.21 and I don't understand why this won't be fixed or at least documented. (for Users who come across this, there are 2 possible workarounds outlined below)

I'm using `EditorGUILayout.PropertyField(...)` as the UI control:

# Workaround 1
A very basic workaround is to manually check `SerializedObject.hasModifiedProperties` alongside `EditorGUI.EndChangeCheck()` to capture the drag-drop being applied.

From expiermentation I've noticed that `hasModifiedProperties` only gets set when the drag-drop completes inside the `EditorGUILayout.PropertyField(...)` so from my ivory tower view it _should_ be a pretty forward case of also setting whatever internal change flag you've got at that point too.

If this is definitely not going to be fixed then there seriously needs to be a review of the documentation of `SerialisedProperty` and `Begin/EndChangeCheck()` to inform users of the cases where it will *not* trigger. This feels like a relatively common use-case.

I've also noticed that using the context menu on the Array property (to delete or duplicate elements) does not trigger change check reports and doesn't set `hasModifiedProperties` either.
# Workaround 2
To workaround _that_ I have to manually check `SerializedProperty.contentHash` across `OnInspectorGUI()` calls and manually set `GUI.changed = true;` so that the code doesn't have to become more polluted than it already has become.
This will also detect the intial Drag-Drop failure.