Inventory API has minimal catalog table usage (join on uid  only), which
makes on-deletion catalog changes insufficient to make movements
disappear transactionally from Inventory API results.
As it may be expected that a set of movements deleted during a single
transaction are atomically removed from Inventory API results, also
change stock table.