I was a bit confused by your saying miners "claim" their reward. I know miners claim the mining rewarding by generation transactions with outputs to their own addresses. But as to the transaction fees, does it simply work in the way that the
transaction fee=input sum-output sum
and this difference goes as money belong to the block of specific miners?
I might be making mistakes and please correct me if I did. Thanks.

So you mean that if such a transaction is submitted to a miner who is willing to confirm it, this 519 Satoshi will belong to the miner still?
I guess this should sound stupid but I just want details clarified. Thank you.

As we know Bitcoin currently has a minimum transaction fee threshold of 0.0001 BTC (10^4 Satoshi). During the process I make analysis of transactions within the recent two years, I found many transactions that has an (input sum-output sum) lower than 0.0001BTC, which is not considered a valid transaction fee (therefore 0 transaction fee).
For example, the tx with ID ef375a852af090f092426c3dc9e8879eef512c338cbf30b83951cff9196c9862   has only 519 more satoshi in the input sum than the outputs, so this single transaction is considered a 0-fee transaction.
My QUESTION is, in the above case, what happens to the difference of 519 Satoshi? Is this still claimed by the miner, or this tiny amount of money simply goes destroyed?

The question might be a bit in-detail into the bitcoind source code. Help from whoever has read or written the code is especially appreciated.
In file addrman.h, tried buckets (vvTried) are maintained in such a way that whenever a new address from the new buckets need to be added into the tried buckets, addrman will check if the tried bucket for this new address is full. If this tried bucket is full, one old address in this tried bucket will be evicted back to the new buckets.

As I have gone through the complete context of bitcoind source code, the above seems to be the only way tried buckets are updated after addrman is initialized. That is, addresses in the tried buckets will be evicted only when new address needs to come in AND the old bucket is full.

My question is, are there any other possible cases that addresses in tried buckets will be updated(altered/deleted)? If not, this should mean that before the tried buckets are full, no entry in the tried buckets will be removed even though some become not reachable(not routable). Will this practically be a problem? Is it good practice to improve the addr. management technique by introducing some routable checks. For example, if some tried addresses become unreachable, we asynchronously remove them and put back to new buckets?

I am in-depth studying about it for my research on inter-node communication and addr. exchanging in Bitcoin. Please just be as technical as possible. Any suggestion is much appreciated.

https://bitcointalk.org/index.php?topic=197323.0
This thread reply should help clarify my question. What I am looking for is code part that deals with relay of unconfirmed transaction.

I have some confusion when I study the transaction relay module in the source code.
As part of protocol every bitcoin node helps relay valid transactions from others so that everyone's transaction can get received by some miner and confirmed.
However, it looks pretty hard for me to find out what reaction is taken when a valid transaction comes to me, given I am not a miner. I expect to see codes that help relay these unconfirmed transactions to nodes I am connecting to, but I did not find clues in the source.

Right now I am only able to get to know the function RelayTransaction() defined in main.cpp and CTxMemPoolEntry which keeps transactions in memory. RelayTransaction() is called when "tx" message is sent as a response to a "getdata" message. But which code describes the part I help relay unconfirmed transactions for others?
I need full understanding for this part to go with my research on synchronization issues in Bitcoin. Anyone who experienced BTC development helping me is particularly appreciated. Thanks.

According to the protocol specific given by BitcoinWiki, after a transaction is broadcast,  ""it may be included in a block that is published to the network". Here comes something trivial: When is the newly confirmed transaction written into a block? Suppose I am an average node and I received a transaction and verified it is valid. What is the next step for me? Do I write this transaction into the latest block? How to make sure all nodes have a specific transaction written consistently into the same block?
I am currently researching network consistency issues and security problems in the Bitcoin system. This problem seems to remains an unsolved issue given I have not misunderstood anything else. I appreciate any help from anyone professional. Thanks in advance.