When a block reward is spent together with other outputs in the wallet and that block reward is later orphaned, the wallet does not show the other funds as available anymore.  Even a `-rescan` is not enough - only `-zapwallettxes` or an explicit `abandontransaction` "recovers" the funds.  I prepared a [test case](https://github.com/domob1812/bitcoin/blob/wallet-bug-invalidated-block-rewards/test/functional/wallet_bug.py) that shows this behaviour.

Is this a known issue or the expected behaviour?  While this situation is something that will presumably not occur in practice (as it requires a long reorg), I wonder if that transaction should be automatically abandoned as it seems clear it won't be able to be confirmed anymore.
GetDatabase().Rewrite();
        // B
        // s
        // u
        GetDatabase().ReloadDbEnv();
    }
    NotifyStatusChanged(this);
    return true;
}
DBErrors CWalletReorderTransactions()
{
    LOCK(cs_);
    WalletBatch batch(GetDatabase());
    // O
    // P
    // F
    typedef stdmultimap<int64_t, CWalletTx*> TxItems;
    TxItems txByTime;
    for (auto& entry  mapWallet)
    {
        CWalletTx* wtx = &entry.second;
        txByTime.insert(stdmake_pair(wtx->nTimeReceived, wtx));
    }
    nOrderPosNext = 0;
    stdvector<int64_t> nOrderPosOffsets;
    for (TxItemsiterator it = txByTime.begin(); it != txByTime.end(); ++it)
    {
        CWalletTx *const pwtx = (*it).second;
        int64_t& nOrderPos = pwtx->nOrderPos;
        if (nOrderPos == -1)