Calling DestroyImmediate from an AssetPostprocessor

We have had some reports from users saying that calling DestroyImmediate during asset postprocessing crashes the editor. We have not been able to reproduce a crash, but in some cases the behaviour is confusing:

1. calling DestroyImmediate on a random asset (other than the one associated with the current asset postprocessor's assetImporter) leaves the asset in an unusable state (AssetDatabase returns null, but asset remains in project browser and can be fixed back to normal state by calling ReimportAll)

2. calling DestroyImmediate on an asset being postprocessed doesn't seem to destroy the asset permanently

to repro 1 - open attached project, reimport asset "menu_close.wav"
to repro 2 - open attached project, reimport asset "menu_open.wav"
( use reimport all to revert the asset back to testable state)